Grouping in a system with multiple media playback protocols

ABSTRACT

While a first playback device is a member of a synchronous media playback group with a second playback device using a first media playback protocol, and after a particular playback setting is enabled using the first media playback protocol, the first playback device receives, from a media source device, a first media stream using a second media playback protocol. The first and second media playback protocols are incompatible. The first playback device determines that the particular playback setting is enabled and that the synchronous media playback group includes the first playback device and the second playback device. Subsequently, the first playback device (i) generates a second media stream based on the received first media stream, the second media stream including information for synchronous playback with the first playback device, and (ii) transmits, to the second playback device, the second media stream using the second media playback protocol.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No.16/853,429, filed on Apr. 20, 2020, titled “Grouping in a System withMultiple Media Playback Protocols,” which claims the benefit of U.S.application Ser. No. 16/215,013, filed on Dec. 10, 2018, titled“Grouping in a System with Multiple Media Playback Protocols,” whichclaims the benefit of U.S. application Ser. No. 15/714,950, filed onSep. 25, 2017, titled “Grouping in a System with Multiple Media PlaybackProtocols,” which claims the benefit of U.S. Provisional App.62/554,566, filed Sep. 5, 2017, titled “Adding a Playback Device to aPlayback Session,” all of which are explicitly incorporated by referenceherein in their entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other elementsdirected to media playback and aspects thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loudsetting were limited until in 2003, when Sonos, Inc. filed for one ofits first patent applications, entitled “Method for Synchronizing AudioPlayback between Multiple Networked Devices,” and began offering a mediaplayback system for sale in 2005. The Sonos Wireless HiFi System enablespeople to experience music from many sources via one or more networkedplayback devices. Through a software control application installed on asmartphone, tablet, or computer, one can play what he or she wants inany room that has a networked playback device. Additionally, using thecontroller, for example, different songs can be streamed to each roomwith a playback device, rooms can be grouped together for synchronousplayback, or the same song can be heard in all rooms synchronously.

Given the ever-growing interest in digital media, there continues to bea need to develop consumer-accessible technologies to further enhancethe listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example media playback system configuration in whichcertain examples may be practiced;

FIG. 2 shows a functional block diagram of an example playback device;

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example controller interface;

FIG. 5 shows an example plurality of network devices;

FIG. 6 shows a function block diagram of an example network microphonedevice;

FIG. 7 shows a flow diagram of an example media playback system;

FIG. 8 shows an example method according to some examples; and

FIG. 9 shows an example method according to some examples.

The drawings are for the purpose of illustrating examples, but it isunderstood that the inventions are not limited to the arrangements andinstrumentalities shown in the drawings.

DETAILED DESCRIPTION I. Overview

Media playback systems may contain networked devices that arecontrollable by device(s) using different media playback protocols. Amedia playback protocol may refer to a set of guidelines a mediaplayback system uses for implementing networking communications betweennetworked devices (e.g., Apple® Airplay®, Sonos® system). In some cases,media playback systems implement more than one media playback protocolto provide a user with a seamless entertainment experience. Forinstance, a user may be able to stream media content to the mediaplayback system through a variety of media source devices and controldevices. These media source devices and control devices may be adedicated controller for the media playback system and/or may be anetwork device (e.g., an iPhone®, iPad® or any other smart phone, tabletor network device (e.g., a networked computer such as a PC or Mac®)) onwhich media playback system controller application software may beinstalled.

One challenge with allowing a media playback system to be compatiblewith multiple media playback protocols is an inability to consistentlycontrol and reflect changes to the media playback system across themultiple protocols. For instance, if a user streams media content tomultiple networked devices in a playback session controlled by one mediaplayback protocol, and then issues playback commands in an interfacecontrolled by another media playback protocol, the playback commandsmight not result in the desired outcome (e.g., the other media playbackprotocol may not know to issue the playback commands to more than onenetworked device).

Users may also configure networked devices to operate in a group forsynchronous playback of media content in a playback session using onemedia playback protocol and then try to stream media content to thegroup in an interface controlled by another media playback protocol. Inthese situations, the network media system may (i) form a group of twoor more networked devices using a first media playback protocol, (ii)determine a group coordinator for the group, and (iii) transmit to amedia source device a group network identity using a second mediaplayback protocol, where the first and second media playback protocolsare incompatible. This may allow the user to view and/or control thenetworked devices as grouped in an interface using a media playbackprotocol that is not compatible with the media playback protocol used togroup the networked devices. A first and second media playback protocolmay be incompatible in that the first media playback protocol is unableto control playback associated with the second media playback protocol,and the second media playback protocol is unable to control playbackassociated with the first media playback protocol.

The disclosed examples describe functions performed by networkeddevices, playback devices, voice enabled devices (VEDs), networkedmicrophone devices (NMDs), audio playback devices (APDs), and videoplayback devices (VPDs). As used herein, the term networked device is aclass of devices that includes, but is not limited to VEDs, NMDs, APDs,and VPDs.

The examples described herein provide a user with a seamless controlover a media playback system via interfaces that use different mediaplayback protocols. A first example may include a network media systemforming a group comprising a first networked device and a secondnetworked device using a first media playback protocol. The networkmedia system includes the first networked device and the secondnetworked device.

The first example may further include the network media systemdetermining a group coordinator for the group using a particular mediaplayback protocol.

The first example may further include the media playback systemtransmitting, to a media source device, a group network identity usinganother media playback protocol. The media source device and at leastone of the first networked device and the second networked device areconfigured to use the particular media playback protocol and the othermedia playback protocol. The particular media playback protocol and theother media playback protocol are incompatible

While some examples described herein may refer to functions performed bygiven actors such as “users” and/or other entities, it should beunderstood that this is for purposes of explanation only. The claimsshould not be interpreted to require action by any such example actorunless explicitly required by the language of the claims themselves. Itwill be understood by one of ordinary skill in the art that thisdisclosure includes numerous other examples.

II. Example Operating Environment

FIG. 1 shows an example configuration of a media playback system 100 inwhich one or more examples disclosed herein may be practiced orimplemented. The media playback system 100 as shown is associated withan example home environment having several rooms and spaces, such as forexample, a master bedroom, an office, a dining room, and a living room.As shown in the example of FIG. 1, the media playback system 100includes playback devices 102-124, control devices 126 and 128, and awired or wireless network router 130. In operation, any of the playbackdevices (PBDs) 102-124 may be voice-enabled devices (VEDs) as describedearlier.

Further discussions relating to the different components of the examplemedia playback system 100 and how the different components may interactto provide a user with a media experience may be found in the followingsections. While discussions herein may generally refer to the examplemedia playback system 100, technologies described herein are not limitedto applications within, among other things, the home environment asshown in FIG. 1. For instance, the technologies described herein may beuseful in environments where multi-zone audio may be desired, such as,for example, a commercial setting like a restaurant, mall or airport, avehicle like a sports utility vehicle (SUV), bus or car, a ship or boat,an airplane, and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device200 that may be configured to be one or more of the playback devices102-124 of the media playback system 100 of FIG. 1. As described above,a playback device (PBD) 200 may include voice-enabled devices (VEDs).

The playback device 200 includes one or more processors 202, softwarecomponents 204, memory 206, audio processing components 208, audioamplifier(s) 210, speaker(s) 212, a network interface 214 includingwireless interface(s) 216 and wired interface(s) 218, and microphone(s)220. In one case, the playback device 200 may not include the speaker(s)212, but rather a speaker interface for connecting the playback device200 to external speakers. In another case, the playback device 200 mayinclude neither the speaker(s) 212 nor the audio amplifier(s) 210, butrather an audio interface for connecting the playback device 200 to anexternal audio amplifier or audio-visual receiver.

In some examples, the one or more processors 202 include one or moreclock-driven computing components configured to process input dataaccording to instructions stored in the memory 206. The memory 206 maybe a tangible, non-transitory computer-readable medium configured tostore instructions executable by the one or more processors 202. Forinstance, the memory 206 may be data storage that can be loaded with oneor more of the software components 204 executable by the one or moreprocessors 202 to achieve certain functions. In one example, thefunctions may involve the playback device 200 retrieving audio data froman audio source or another playback device. In another example, thefunctions may involve the playback device 200 sending audio data toanother device or playback device on a network. In yet another example,the functions may involve pairing of the playback device 200 with one ormore playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 200 synchronizingplayback of audio content with one or more other playback devices.During synchronous playback, a listener will preferably not be able toperceive time-delay differences between playback of the audio content bythe playback device 200 and the one or more other playback devices. U.S.Pat. No. 8,234,395 entitled, “System and method for synchronizingoperations among a plurality of independently clocked digital dataprocessing devices,” which is hereby incorporated by reference, providesin more detail some examples for audio playback synchronization amongplayback devices.

The memory 206 may further be configured to store data associated withthe playback device 200, such as one or more zones and/or zone groupsthe playback device 200 is a part of, audio sources accessible by theplayback device 200, or a playback queue that the playback device 200(or some other playback device) may be associated with. The data may bestored as one or more state variables that are periodically updated andused to describe the state of the playback device 200. The memory 206may also include the data associated with the state of the other devicesof the media system, and shared from time to time among the devices sothat one or more of the devices have the most recent data associatedwith the system. Other examples are also possible.

The audio processing components 208 may include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor (DSP), and soon. In one examples, one or more of the audio processing components 208may be a subcomponent of the one or more processors 202. In one example,audio content may be processed and/or intentionally altered by the audioprocessing components 208 to produce audio signals. The produced audiosignals may then be provided to the audio amplifier(s) 210 foramplification and playback through speaker(s) 212. Particularly, theaudio amplifier(s) 210 may include devices configured to amplify audiosignals to a level for driving one or more of the speakers 212. Thespeaker(s) 212 may include an individual transducer (e.g., a “driver”)or a complete speaker system involving an enclosure with one or moredrivers. A particular driver of the speaker(s) 212 may include, forexample, a subwoofer (e.g., for low frequencies), a mid-range driver(e.g., for middle frequencies), and/or a tweeter (e.g., for highfrequencies). In some cases, each transducer in the one or more speakers212 may be driven by an individual corresponding audio amplifier of theaudio amplifier(s) 210. In addition to producing analog signals forplayback by the playback device 200, the audio processing components 208may be configured to process audio content to be sent to one or moreother playback devices for playback.

Audio content to be processed and/or played back by the playback device200 may be received from an external source, such as via an audioline-in input connection (e.g., an auto-detecting 3.5 mm audio line-inconnection) or the network interface 214.

The network interface 214 may be configured to facilitate a data flowbetween the playback device 200 and one or more other devices on a datanetwork. As such, the playback device 200 may be configured to receiveaudio content over the data network from one or more other playbackdevices in communication with the playback device 200, network deviceswithin a local area network, or audio content sources over a wide areanetwork such as the Internet. The playback device 200 may transmitmetadata to and/or receive metadata from other devices on the network,including but not limited to components of the networked microphonesystem disclosed and described herein. In one example, the audio contentand other signals (e.g., metadata and other signals) transmitted andreceived by the playback device 200 may be transmitted in the form ofdigital packet data containing an Internet Protocol (IP)-based sourceaddress and IP-based destination addresses. In such a case, the networkinterface 214 may be configured to parse the digital packet data suchthat the data destined for the playback device 200 is properly receivedand processed by the playback device 200.

As shown, the network interface 214 may include wireless interface(s)216 and wired interface(s) 218. The wireless interface(s) 216 mayprovide network interface functions for the playback device 200 towirelessly communicate with other devices (e.g., other playbackdevice(s), speaker(s), receiver(s), network device(s), control device(s)within a data network the playback device 200 is associated with) inaccordance with a communication protocol (e.g., any wireless standardincluding IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4Gmobile communication standard, and so on). The wired interface(s) 218may provide network interface functions for the playback device 200 tocommunicate over a wired connection with other devices in accordancewith a communication protocol (e.g., IEEE 802.3). While the networkinterface 214 shown in FIG. 2 includes both wireless interface(s) 216and wired interface(s) 218, the network interface 214 may in someexamples include only wireless interface(s) or only wired interface(s).

The microphone(s) 220 may be arranged to detect sound in the environmentof the playback device 200. For instance, the microphone(s) may bemounted on an exterior wall of a housing of the playback device. Themicrophone(s) may be any type of microphone now known or later developedsuch as a condenser microphone, electret condenser microphone, or adynamic microphone. The microphone(s) may be sensitive to a portion ofthe frequency range of the speaker(s) 220. One or more of the speaker(s)220 may operate in reverse as the microphone(s) 220. In some aspects,the playback device 200 might not have microphone(s) 220.

In one example, the playback device 200 and one other playback devicemay be paired to play two separate audio components of audio content.For instance, playback device 200 may be configured to play a leftchannel audio component, while the other playback device may beconfigured to play a right channel audio component, thereby producing orenhancing a stereo effect of the audio content. The paired playbackdevices (also referred to as “bonded playback devices”, “bonded group”,or “stereo pair”) may further play audio content in synchrony with otherplayback devices.

In another example, the playback device 200 may be sonicallyconsolidated with one or more other playback devices to form a single,consolidated playback device. A consolidated playback device may beconfigured to process and reproduce sound differently than anunconsolidated playback device or playback devices that are paired,because a consolidated playback device may have additional speakerdrivers through which audio content may be rendered. For instance, ifthe playback device 200 is a playback device designed to render lowfrequency range audio content (i.e. a subwoofer), the playback device200 may be consolidated with a playback device designed to render fullfrequency range audio content. In such a case, the full frequency rangeplayback device, when consolidated with the low frequency playbackdevice 200, may be configured to render only the mid and high frequencycomponents of audio content, while the low frequency range playbackdevice 200 renders the low frequency component of the audio content. Theconsolidated playback device may further be paired with a singleplayback device or yet another consolidated playback device.

By way of illustration, Sonos, Inc. presently offers (or has offered)for sale certain playback devices including a “PLAY:1,” “PLAY:3,”“PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any otherpast, present, and/or future playback devices may additionally oralternatively be used to implement the playback devices disclosedherein. Additionally, it is understood that a playback device is notlimited to the example illustrated in FIG. 2 or to the Sonos productofferings. For example, a playback device may include a wired orwireless headphone. In another example, a playback device may include orinteract with a docking station for personal mobile media playbackdevices. In yet another example, a playback device may be integral toanother device or component such as a television, a lighting fixture, orsome other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 100 of FIG. 1, theenvironment may have one or more playback zones, each with one or moreplayback devices. The media playback system 100 may be established withone or more playback zones, after which one or more zones may be added,or removed to arrive at the example configuration shown in FIG. 1. Eachzone may be given a name according to a different room or space such asan office, bathroom, master bedroom, bedroom, kitchen, dining room,living room, and/or balcony. In one case, a single playback zone mayinclude multiple rooms or spaces. In another case, a single room orspace may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office,and bedroom zones each have one playback device, while the living roomand master bedroom zones each have multiple playback devices. In theliving room zone, playback devices 104, 106, 108, and 110 may beconfigured to play audio content in synchrony as individual playbackdevices, as one or more bonded playback devices, as one or moreconsolidated playback devices, or any combination thereof. Similarly, inthe case of the master bedroom, playback devices 122 and 124 may beconfigured to play audio content in synchrony as individual playbackdevices, as a bonded playback device, or as a consolidated playbackdevice.

In one example, one or more playback zones in the environment of FIG. 1may each be playing different audio content. For instance, the user maybe grilling in the balcony zone and listening to hip hop music beingplayed by the playback device 102 while another user may be preparingfood in the kitchen zone and listening to classical music being playedby the playback device 114. In another example, a playback zone may playthe same audio content in synchrony with another playback zone. Forinstance, the user may be in the office zone where the playback device118 is playing the same rock music that is being playing by playbackdevice 102 in the balcony zone. In such a case, playback devices 102 and118 may be playing the rock music in synchrony such that the user mayseamlessly (or at least substantially seamlessly) enjoy the audiocontent that is being played out-loud while moving between differentplayback zones. Synchronization among playback zones may be achieved ina manner similar to that of synchronization among playback devices, asdescribed in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system100 may be dynamically modified, and in some examples, the mediaplayback system 100 supports numerous configurations. For instance, if auser physically moves one or more playback devices to or from a zone,the media playback system 100 may be reconfigured to accommodate thechange(s). For instance, if the user physically moves the playbackdevice 102 from the balcony zone to the office zone, the office zone maynow include both the playback device 118 and the playback device 102.The playback device 102 may be paired or grouped with the office zoneand/or renamed if so desired via a control device such as the controldevices 126 and 128. On the other hand, if the one or more playbackdevices are moved to a particular area in the home environment that isnot already a playback zone, a new playback zone may be created for theparticular area.

Further, different playback zones of the media playback system 100 maybe dynamically combined into zone groups or split up into individualplayback zones. For instance, the dining room zone and the kitchen zonemay be combined into a zone group for a dinner party such that playbackdevices 112 and 114 may render (e.g., play back) audio content insynchrony. On the other hand, the living room zone may be split into atelevision zone including playback device 104, and a listening zoneincluding playback devices 106, 108, and 110, if the user wishes tolisten to music in the living room space while another user wishes towatch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300that may be configured to be one or both of the control devices 126 and128 of the media playback system 100. As shown, the control device 300may include one or more processors 302, memory 304, a network interface306, a user interface 308, microphone(s) 310, and software components312. In one example, the control device 300 may be a dedicatedcontroller for the media playback system 100. In another example, thecontrol device 300 may be a network device on which media playbacksystem controller application software may be installed, such as forexample, an iPhone®, iPad® or any other smart phone, tablet or networkdevice (e.g., a networked computer such as a PC or Mae).

The one or more processors 302 may be configured to perform functionsrelevant to facilitating user access, control, and configuration of themedia playback system 100. The memory 304 may be data storage that canbe loaded with one or more of the software components executable by theone or more processors 302 to perform those functions. The memory 304may also be configured to store the media playback system controllerapplication software and other data associated with the media playbacksystem 100 and the user.

In one example, the network interface 306 may be based on an industrystandard (e.g., infrared, radio, wired standards including IEEE 802.3,wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n,802.11ac, 802.15, 3G, 4G, or 5G mobile communication standards, and soon). The network interface 306 may provide a means for the controldevice 300 to communicate with other devices in the media playbacksystem 100. In one example, data and information (e.g., such as a statevariable) may be communicated between control device 300 and otherdevices via the network interface 306. For instance, playback zone andzone group configurations in the media playback system 100 may bereceived by the control device 300 from a playback device or anothernetwork device, or transmitted by the control device 300 to anotherplayback device or network device via the network interface 306. In somecases, the other network device may be another control device.

Playback device control commands such as volume control and audioplayback control may also be communicated from the control device 300 toa playback device via the network interface 306. As suggested above,changes to configurations of the media playback system 100 may also beperformed by a user using the control device 300. The configurationchanges may include adding/removing one or more playback devices to/froma zone, adding/removing one or more zones to/from a zone group, forminga bonded or consolidated player, separating one or more playback devicesfrom a bonded or consolidated player, among others. Accordingly, thecontrol device 300 may sometimes be referred to as a controller, whetherthe control device 300 is a dedicated controller or a network device onwhich media playback system controller application software isinstalled.

Control device 300 may include microphone(s) 310. Microphone(s) 310 maybe arranged to detect sound in the environment of the control device300. Microphone(s) 310 may be any type of microphone now known or laterdeveloped such as a condenser microphone, electret condenser microphone,or a dynamic microphone. The microphone(s) may be sensitive to a portionof a frequency range. Two or more microphones 310 may be arranged tocapture location information of an audio source (e.g., voice, audiblesound) and/or to assist in filtering background noise.

The user interface 308 of the control device 300 may be configured tofacilitate user access and control of the media playback system 100, byproviding a controller interface such as the example controllerinterface 400 shown in FIG. 4. The controller interface 400 includes aplayback control region 410, a playback zone region 420, a playbackstatus region 430, a playback queue region 440, and an audio contentsources region 450. The user interface 400 as shown is just one exampleof a user interface that may be provided on a network device such as thecontrol device 300 of FIG. 3 (and/or the control devices 126 and 128 ofFIG. 1) and accessed by users to control a media playback system such asthe media playback system 100. Other user interfaces of varying formats,styles, and interactive sequences may alternatively be implemented onone or more network devices to provide comparable control access to amedia playback system.

The playback control region 410 may include selectable (e.g., by way oftouch or by using a cursor) icons to cause playback devices in aselected playback zone or zone group to play or pause, fast forward,rewind, skip to next, skip to previous, enter/exit shuffle mode,enter/exit repeat mode, enter/exit cross fade mode. The playback controlregion 410 may also include selectable icons to modify equalizationsettings, and playback volume, among other possibilities.

The playback zone region 420 may include representations of playbackzones within the media playback system 100. In some examples, thegraphical representations of playback zones may be selectable to bringup additional selectable icons to manage or configure the playback zonesin the media playback system, such as a creation of bonded zones,creation of zone groups, separation of zone groups, and renaming of zonegroups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of thegraphical representations of playback zones. The “group” icon providedwithin a graphical representation of a particular zone may be selectableto bring up options to select one or more other zones in the mediaplayback system to be grouped with the particular zone. Once grouped,playback devices in the zones that have been grouped with the particularzone will be configured to play audio content in synchrony with theplayback device(s) in the particular zone. Analogously, a “group” iconmay be provided within a graphical representation of a zone group. Inthis case, the “group” icon may be selectable to bring up options todeselect one or more zones in the zone group to be removed from the zonegroup. Other interactions and implementations for grouping andungrouping zones via a user interface such as the user interface 400 arealso possible. The representations of playback zones in the playbackzone region 420 may be dynamically updated as playback zone or zonegroup configurations are modified.

The playback status region 430 may include graphical representations ofaudio content that is presently being played, previously played, orscheduled to play next in the selected playback zone or zone group. Theselected playback zone or zone group may be visually distinguished onthe user interface, such as within the playback zone region 420 and/orthe playback status region 430. The graphical representations mayinclude track title, artist name, album name, album year, track length,and other relevant information that may be useful for the user to knowwhen controlling the media playback system via the user interface 400.

The playback queue region 440 may include graphical representations ofaudio content in a playback queue associated with the selected playbackzone or zone group. In some examples, each playback zone or zone groupmay be associated with a playback queue containing informationcorresponding to zero or more audio items for playback by the playbackzone or zone group. For instance, each audio item in the playback queuemay comprise a uniform resource identifier (URI), a uniform resourcelocator (URL) or some other identifier that may be used by a playbackdevice in the playback zone or zone group to find and/or retrieve theaudio item from a local audio content source or a networked audiocontent source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in whichcase information corresponding to each audio item in the playlist may beadded to the playback queue. In another example, audio items in aplayback queue may be saved as a playlist. In a further example, aplayback queue may be empty, or populated but “not in use” when theplayback zone or zone group is playing continuously streaming audiocontent, such as Internet radio that may continue to play untilotherwise stopped, rather than discrete audio items that have playbackdurations. In an alternative example, a playback queue can includeInternet radio and/or other streaming audio content items and be “inuse” when the playback zone or zone group is playing those items. Otherexamples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,”playback queues associated with the affected playback zones or zonegroups may be cleared or re-associated. For example, if a first playbackzone including a first playback queue is grouped with a second playbackzone including a second playback queue, the established zone group mayhave an associated playback queue that is initially empty, that containsaudio items from the first playback queue (such as if the secondplayback zone was added to the first playback zone), that contains audioitems from the second playback queue (such as if the first playback zonewas added to the second playback zone), or a combination of audio itemsfrom both the first and second playback queues. Subsequently, if theestablished zone group is ungrouped, the resulting first playback zonemay be re-associated with the previous first playback queue, or beassociated with a new playback queue that is empty or contains audioitems from the playback queue associated with the established zone groupbefore the established zone group was ungrouped. Similarly, theresulting second playback zone may be re-associated with the previoussecond playback queue, or be associated with a new playback queue thatis empty, or contains audio items from the playback queue associatedwith the established zone group before the established zone group wasungrouped. Other examples are also possible.

Referring back to the user interface 400 of FIG. 4, the graphicalrepresentations of audio content in the playback queue region 440 mayinclude track titles, artist names, track lengths, and other relevantinformation associated with the audio content in the playback queue. Inone example, graphical representations of audio content may beselectable to bring up additional selectable icons to manage and/ormanipulate the playback queue and/or audio content represented in theplayback queue. For instance, a represented audio content may be removedfrom the playback queue, moved to a different position within theplayback queue, or selected to be played immediately, or after anycurrently playing audio content, among other possibilities. A playbackqueue associated with a playback zone or zone group may be stored in amemory on one or more playback devices in the playback zone or zonegroup, on a playback device that is not in the playback zone or zonegroup, and/or some other designated device.

The audio content sources region 450 may include graphicalrepresentations of selectable audio content sources from which audiocontent may be retrieved and played by the selected playback zone orzone group. Discussions pertaining to audio content sources may be foundin the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zonegroup may be configured to retrieve for playback audio content (e.g.according to a corresponding URI or URL for the audio content) from avariety of available audio content sources. In one example, audiocontent may be retrieved by a playback device directly from acorresponding audio content source (e.g., a line-in connection). Inanother example, audio content may be provided to a playback device overa network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or moreplayback devices in a media playback system such as the media playbacksystem 100 of FIG. 1, local music libraries on one or more networkdevices (such as a control device, a network-enabled personal computer,or a networked-attached storage (NAS), for example), streaming audioservices providing audio content via the Internet (e.g., the cloud), oraudio sources connected to the media playback system via a line-in inputconnection on a playback device or network devise, among otherpossibilities.

In some examples, audio content sources may be regularly added orremoved from a media playback system such as the media playback system100 of FIG. 1. In one example, an indexing of audio items may beperformed whenever one or more audio content sources are added, removedor updated. Indexing of audio items may involve scanning foridentifiable audio items in all folders/directory shared over a networkaccessible by playback devices in the media playback system, andgenerating or updating an audio content database containing metadata(e.g., title, artist, album, track length, among others) and otherassociated information, such as a URI or URL for each identifiable audioitem found. Other examples for managing and maintaining audio contentsources may also be possible.

The above discussions relating to playback devices, controller devices,playback zone configurations, and media content sources provide onlysome examples of operating environments within which functions andmethods described below may be implemented. Other operating environmentsand configurations of media playback systems, playback devices, andnetwork devices not explicitly described herein may also be applicableand suitable for implementation of the functions and methods.

e. Example Plurality of Networked Devices

FIG. 5 shows an example plurality of networked devices 500 that can beconfigured to provide an audio playback experience with voice control.One having ordinary skill in the art will appreciate that the devicesshown in FIG. 5 are for illustrative purposes only, and variationsincluding different and/or additional (or fewer) devices may bepossible. As shown, the plurality of networked devices 500 includescomputing devices 504, 506, and 508; network microphone devices (NMDs)512, 514, and 516; playback devices (PBDs) 532, 534, 536, and 538; and acontroller device (CR) 522. As described previously, any one or more (orall) of the NMDs 512-16, PBDs 532-38, and/or CR 522 may be voice-enableddevices (VEDs).

Each of the plurality of networked devices 500 are network-capabledevices that can establish communication with one or more other devicesin the plurality of devices according to one or more network protocols,such as NFC, Bluetooth™, Ethernet, and IEEE 802.11, among otherexamples, over one or more types of networks, such as wide area networks(WAN), local area networks (LAN), and personal area networks (PAN),among other possibilities.

As shown, the computing devices 504, 506, and 508 are part of a cloudnetwork 502. The cloud network 502 may include additional computingdevices (not shown). In one example, the computing devices 504, 506, and508 may be different servers. In another example, two or more of thecomputing devices 504, 506, and 508 may be modules of a single server.Analogously, each of the computing device 504, 506, and 508 may includeone or more modules or servers. For ease of illustration purposesherein, each of the computing devices 504, 506, and 508 may beconfigured to perform particular functions within the cloud network 502.For instance, computing device 508 may be a source of audio content fora streaming music service.

As shown, the computing device 504 may be configured to interface withNMDs 512, 514, and 516 via communication path 542. NMDs 512, 514, and516 may be components of one or more “Smart Home” systems. In one case,NMDs 512, 514, and 516 may be physically distributed throughout ahousehold, similar to the distribution of devices shown in FIG. 1. Inanother case, two or more of the NMDs 512, 514, and 516 may bephysically positioned within relative close proximity of one another.Communication path 542 may comprise one or more types of networks, suchas a WAN including the Internet, LAN, and/or PAN, among otherpossibilities.

In one example, one or more of the NMDs 512, 514, and 516 are devicesconfigured primarily for audio detection. In another example, one ormore of the NMDs 512, 514, and 516 may be components of devices havingvarious primary utilities. For instance, as discussed above inconnection to FIGS. 2 and 3, one or more of NMDs 512, 514, and 516 maybe (or at least may include or be a component of) the microphone(s) 220of playback device 200 or the microphone(s) 310 of network device 300.Further, in some cases, one or more of NMDs 512, 514, and 516 may be (orat least may include or be a component of) the playback device 200 ornetwork device 300. In an example, one or more of NMDs 512, 514, and/or516 may include multiple microphones arranged in a microphone array. Insome examples, one or more of NMDs 512, 514, and/or 516 may be amicrophone on a mobile computing device (e.g., a smartphone, tablet, orother computing device).

As shown, the computing device 506 is configured to interface with CR522 and PBDs 532, 534, 536, and 538 via communication path 544. In oneexample, CR 522 may be a network device such as the network device 200of FIG. 2. Accordingly, CR 522 may be configured to provide thecontroller interface 400 of FIG. 4. Similarly, PBDs 532, 534, 536, and538 may be playback devices such as the playback device 300 of FIG. 3.As such, PBDs 532, 534, 536, and 538 may be physically distributedthroughout a household as shown in FIG. 1. For illustration purposes,PBDs 536 and 538 are shown as members of a bonded zone 530, while PBDs532 and 534 are members of their own respective zones. As describedabove, the PBDs 532, 534, 536, and 538 may be dynamically bonded,grouped, unbonded, and ungrouped. Communication path 544 may compriseone or more types of networks, such as a WAN including the Internet,LAN, and/or PAN, among other possibilities.

In one example, as with NMDs 512, 514, and 516, CR 522 and PBDs 532,534, 536, and 538 may also be components of one or more “Smart Home”systems. In one case, PBDs 532, 534, 536, and 538 may be distributedthroughout the same household as the NMDs 512, 514, and 516. Further, assuggested above, one or more of PBDs 532, 534, 536, and 538 may be oneor more of NMDs 512, 514, and 516. For example, any one or more (orperhaps all) of NMDs 512-16, PBDs 532-38, and/or CR 522 may bevoice-enabled devices (VEDs).

The NMDs 512, 514, and 516 may be part of a local area network, and thecommunication path 542 may include an access point that links the localarea network of the NMDs 512, 514, and 516 to the computing device 504over a WAN (communication path not shown). Likewise, each of the NMDs512, 514, and 516 may communicate with each other via such an accesspoint.

Similarly, CR 522 and PBDs 532, 534, 536, and 538 may be part of a localarea network and/or a local playback network as discussed in previoussections, and the communication path 544 may include an access pointthat links the local area network and/or local playback network of CR522 and PBDs 532, 534, 536, and 538 to the computing device 506 over aWAN. As such, each of the CR 522 and PBDs 532, 534, 536, and 538 mayalso communicate with each over such an access point.

In one example, communication paths 542 and 544 may comprise the sameaccess point. In an example, each of the NMDs 512, 514, and 516, CR 522,and PBDs 532, 534, 536, and 538 may access the cloud network 502 via thesame access point for a household.

As shown in FIG. 5, each of the NMDs 512, 514, and 516, CR 522, and PBDs532, 534, 536, and 538 may also directly communicate with one or more ofthe other devices via communication means 546. Communication means 546as described herein may involve and/or include one or more forms ofcommunication between the devices, according to one or more networkprotocols, over one or more types of networks, and/or may involvecommunication via one or more other network devices. For instance,communication means 546 may include one or more of for example,Bluetooth™ (IEEE 802.15), NFC, Wireless direct, and/or Proprietarywireless, among other possibilities.

In one example, CR 522 may communicate with NMD 512 over Bluetooth™, andcommunicate with PBD 534 over another local area network. In anotherexample, NMD 514 may communicate with CR 522 over another local areanetwork, and communicate with PBD 536 over Bluetooth™. In a furtherexample, each of the PBDs 532, 534, 536, and 538 may communicate witheach other according to a spanning tree protocol over a local playbacknetwork, while each communicating with CR 522 over a local area network,different from the local playback network. Other examples are alsopossible.

In some cases, communication means between the NMDs 512, 514, and 516,CR 522, and PBDs 532, 534, 536, and 538 may be different (or perhapschange) depending on types of communication requirements between thedevices, network conditions, and/or latency demands. For instance,communication means 546 may be used when NMD 516 is first introduced tothe household with the PBDs 532, 534, 536, and 538. In one case, the NMD516 may transmit identification information corresponding to the NMD 516to PBD 538 via NFC, and PBD 538 may in response, transmit local areanetwork information to NMD 516 via NFC (or some other form ofcommunication). However, once NMD 516 has been configured within thehousehold, communication means between NMD 516 and PBD 538 may change.For instance, NMD 516 may subsequently communicate with PBD 538 viacommunication path 542, the cloud network 502, and communication path544. In another example, the NMDs and PBDs may never communicate vialocal communications means 546. In a further example, the NMDs and PBDsmay communicate primarily via local communications means 546. Otherexamples are also possible.

In an illustrative example, NMDs 512, 514, and 516 may be configured toreceive voice inputs to control PBDs 532, 534, 536, and 538. Theavailable control commands may include any media playback systemcontrols previously discussed, such as playback volume control, playbacktransport controls, music source selection, and grouping, among otherpossibilities. In one instance, NMD 512 may receive a voice input tocontrol one or more of the PBDs 532, 534, 536, and 538. In response toreceiving the voice input, NMD 512 may transmit via communication path542, the voice input to computing device 504 for processing. In oneexample, the computing device 504 may convert the voice input to anequivalent text command, and parse the text command to identify acommand. Computing device 504 may then subsequently transmit the textcommand to the computing device 506, and computing device 506 in turnmay then control one or more of PBDs 532-538 to execute the command. Inanother example, the computing device 504 may convert the voice input toan equivalent text command, and then subsequently transmit the textcommand to the computing device 506. The computing device 506 may thenparse the text command to identify one or more playback commands, andthen computing device 506 may additionally control one or more of PBDs532-538 to execute the command.

For instance, if the text command is “Play ‘Track 1’ by ‘Artist 1’ from‘Streaming Service 1’ in ‘Zone 1’,” The computing device 506 mayidentify (i) a URL for “Track 1” by “Artist 1” available from “StreamingService 1,” and (ii) at least one playback device in “Zone 1.” In thisexample, the URL for “Track 1” by “Artist 1” from “Streaming Service 1”may be a URL pointing to computing device 508, and “Zone 1” may be thebonded zone 530. As such, upon identifying the URL and one or both ofPBDs 536 and 538, the computing device 506 may transmit viacommunication path 544 to one or both of PBDs 536 and 538, theidentified URL for playback. One or both of PBDs 536 and 538 mayresponsively retrieve audio content from the computing device 508according to the received URL, and begin playing “Track 1” by “Artist 1”from “Streaming Service 1.”

One having ordinary skill in the art will appreciate that the above isjust one illustrative example, and that other implementations are alsopossible. In one case, operations performed by one or more of theplurality of network devices 500, as described above, may be performedby one or more other devices in the plurality of network devices 500.For instance, the conversion from voice input to the text command may bealternatively, partially, or wholly performed by another device ordevices, such as CR 522, NMD 512, computing device 506, PBD 536, and/orPBD 538. Analogously, the identification of the URL may bealternatively, partially, or wholly performed by another device ordevices, such as NMD 512, computing device 504, PBD 536, and/or PBD 538.

f. Example Network Microphone Device

FIG. 6 shows a function block diagram of an example network microphonedevice 600 that may be configured to be one or more of NMDs 512, 514,and 516 of FIG. 5, and/or any of the VEDs disclosed and describedherein. As shown, the network microphone device 600 includes one or moreprocessors 602, tangible, non-transitory computer-readable memory 604, amicrophone array 606 (e.g., one or more microphones), a networkinterface 608, a user interface 610, software components 612, andspeaker(s) 614. One having ordinary skill in the art will appreciatethat other network microphone device configurations and arrangements arealso possible. For instance, network microphone devices mayalternatively exclude the speaker(s) 614 or have a single microphoneinstead of microphone array 606.

The one or more processors 602 may include one or more processors and/orcontrollers, which may take the form of a general or special-purposeprocessor or controller. For instance, the one or more processors 602may include microprocessors, microcontrollers, application-specificintegrated circuits, digital signal processors, and the like. Thetangible, non-transitory computer-readable memory 604 may be datastorage that can be loaded with one or more of the software componentsexecutable by the one or more processors 602 to perform those functions.Accordingly, memory 604 may comprise one or more non-transitorycomputer-readable storage mediums, examples of which may includevolatile storage mediums such as random access memory, registers, cache,etc. and non-volatile storage mediums such as read-only memory, ahard-disk drive, a solid-state drive, flash memory, and/or anoptical-storage device, among other possibilities.

The microphone array 606 may be a plurality of microphones arranged todetect sound in the environment of the network microphone device 600.Microphone array 606 may include any type of microphone now known orlater developed such as a condenser microphone, electret condensermicrophone, or a dynamic microphone, among other possibilities. In oneexample, the microphone array may be arranged to detect audio from oneor more directions relative to the network microphone device. Themicrophone array 606 may be sensitive to a portion of a frequency range.In one example, a first subset of the microphone array 606 may besensitive to a first frequency range, while a second subset of themicrophone array may be sensitive to a second frequency range. Themicrophone array 606 may further be arranged to capture locationinformation of an audio source (e.g., voice, audible sound) and/or toassist in filtering background noise. Notably, in some examples, themicrophone array may consist of only a single microphone, rather than aplurality of microphones.

The network interface 608 may be configured to facilitate wirelessand/or wired communication between various network devices, such as, inreference to FIG. 5, CR 522, PBDs 532-538, computing devices 504-508 incloud network 502, and other network microphone devices, among otherpossibilities. As such, network interface 608 may take any suitable formfor carrying out these functions, examples of which may include anEthernet interface, a serial bus interface (e.g., FireWire, USB 2.0,etc.), a chipset and antenna adapted to facilitate wirelesscommunication, and/or any other interface that provides for wired and/orwireless communication. In one example, the network interface 608 may bebased on an industry standard (e.g., infrared, radio, wired standardsincluding IEEE 802.3, wireless standards including IEEE 802.11a,802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communicationstandard, and so on).

The user interface 610 of the network microphone device 600 may beconfigured to facilitate user interactions with the network microphonedevice. In one example, the user interface 610 may include one or moreof physical buttons, graphical interfaces provided on touch sensitivescreen(s) and/or surface(s), among other possibilities, for a user todirectly provide input to the network microphone device 600. The userinterface 610 may further include one or more of lights and thespeaker(s) 614 to provide visual and/or audio feedback to a user. In oneexample, the network microphone device 600 may further be configured toplayback audio content via the speaker(s) 614.

f. Example Media Playback Environment

It may be desirable in some instances for a user to control and playmedia content on networked devices where the media content may be playedusing a first media playback protocol and controlled using a first mediaplayback protocol and/or a second media playback protocol. In somecircumstances, media playback systems may be able to receive mediacontent from one or more media sources using different media playbackprotocols. However, this method might not allow for consistent controlacross the two or more media playback protocols (e.g., starting mediastreams, issuing playback commands, grouping networked devices,controlling volume, etc.). To enable control of the networked devicesacross different media playback protocols, in some examples, networkeddevices may include hardware and/or software components to facilitatecommunication and control of networked devices using one or moredifferent media playback protocols. This may be beneficial because itallows a user's actions using one media playback protocol to beconverted and/or reflected in another media playback protocol, providingthe user with a seamless experience independent of the media playbackprotocol that the user is using.

For instance, a user may have a media playback system including one ormore networked devices. The one or more networked devices may be able toreceive media from, and be controlled by, a first control device orapplication on the first control device using one media playbackprotocol (e.g., an iPhone® using Airplay). The one or more networkeddevices may also be able to retrieve media over a wide area network(WAN) from a remote server and be controlled by a second control deviceor application (e.g., a Sonos® controller) using another media playbackprotocol. If the user starts a media stream to or media playback at theone or more networked devices using one media playback protocol on afirst control device, the user may be able to control (e.g.,play/pause/skip song) the media stream using another media playbackprotocol on a second control device. This feature provides the user withthe freedom to stream and control media content to networked devicesusing whichever control device is most convenient to the user. In someaspects, the first control device and the second control device may bethe same device (e.g., computing device, mobile phone, tablet, etc.).

FIG. 7 shows a flow diagram of an example media playback system 700 thatincludes a media source device 702 and a control device 704 which areconfigured to control a first networked device 706 and a secondnetworked device 714. First networked device 706 and second networkeddevice 714 may be configured to play back media synchronously orindependently. First networked device 706 and second networked device714 may be any of playback devices 102-124 in FIG. 1, playback device200 in FIG. 2, NMDs 512, 514, 516, and PBDs 532, 534, 536, 538 in FIG.5, and/or network microphone device 600 in FIG. 6.

First networked device 706 includes a first protocol interface 708, asecond protocol interface 710, and a media renderer 712. Secondnetworked device 714 includes a first protocol interface 716, a secondprotocol interface 718, and a media renderer 720. Media source device702 and first protocol interfaces 708 and 716 may operate according tofirst media playback protocol 746. Control device 704 and secondprotocol interfaces 710 and 718 are part of a second media playbackprotocol 748.

Media source device 702 may be a network device from which firstnetworked device 706 and second networked device 714 receive mediacontent in a particular media playback protocol. Media source device 702may include similar components to control device 300 of FIG. 3, and mayoperate using a particular media playback protocol, such as first mediaplayback protocol 746. For example, media source device 702 may includean iPhone®, iPad®, or any other smart phone, tablet or network devicethat uses a particular media playback protocol (e.g., airplay). Mediasource device 702 communicates with first protocol interface 708 offirst networked device 706 via a network connection. Control commands infirst media playback protocol may be communicated as control information726 via the network connection. Streaming audio content 740 may also becommunicated via the network connection. In some instances, controlinformation 726 is communicated along with audio content 740, while inother instances control information 726 is communicated separately fromaudio content 740. Media source device 702 can communicate with firstprotocol interface 716 of second networked device 714 via controlinformation 728 and audio content 742. Control information 722 and 726may be transmitted over the respective network connections and beconfigured to control media playback of first networked device 706 andsecond networked device 714, respectively.

Control device 704 may be a network device that transmits controlcommands or instructions to first networked device 706 and secondnetworked device 714. Control device 704 may include similar componentsto control device 300 of FIG. 3. In one example, control device 704 maybe a dedicated controller for control environment 700. In anotherexample, control device 704 may be a network device or other computingdevice on which a media playback system controller application may beinstalled, such as an iPhone®, iPad®, or any other smart phone, tablet,or network device. In yet other examples, control device 704 may be thesame device as media source device 702. In other words, control device704 may be configured to use the first media playback protocol 746 andthe second media playback protocol 748. Control device 704 communicateswith second protocol interface 710 of first networked device 706 viacontrol information 722 and audio information 732. Control information722 may include control commands to control media playback on firstnetworked device 706 and/or second networked device 714.

In some examples, first networked device 706 and second networked device714 may be grouped to play back media synchronously in second mediaplayback protocol 748. In a group, first networked device 706 may act asa group coordinator. As group coordinator, first networked device 706may be responsible for receiving control information from control device704 and transmitting the control information to other group members. Forexample, control device 704 may send additional control information 722such as playback commands to first networked device 706 when firstnetworked device 706 is acting as a group coordinator, and first networkdevice 706 may communicate the control information to second networkeddevice 714. For example, the control commands controlling the secondnetworked device 706 may be transmitted from second protocol interface710 of first networked device 706 to second protocol interface 718 ofsecond networked device 714.

First networked device 706 may be a networked device such as any of avoice enabled device (VED), networked microphone device (NMD), audioplayback device (APD), video playback device (VPD), or any othernetworked device. These devices may optionally include one or moremicrophones and one or more speakers and/or speaker drivers. Firstnetworked device 706 includes a first protocol interface 708, a secondprotocol interface 710, and a media renderer 712. First networked device706 may be configured to receive audio content 740 from media sourcedevice 702 and control information 722 from control device 704. Firstnetworked device 706 may further be configured to send audio information732 (e.g., metadata such as album information, cover art, artistinformation, track name, radio station name, etc.) to control device704. First networked device 706 may be further configured to send and/orreceive control information 750 to/from second networked device 714.

First protocol interface 708 may be a hardware and/or software componentconfigured to (i) receive media or audio content in an audio stream 740sent by media source device 702, (ii) convert (e.g., decrypt,decompress, and/or decode) audio content 740, and (iii) send theconverted audio 740 to media renderer 712. First protocol interface 708may additionally be configured to (i) receive control information 724from second protocol interface 710 and (ii) send audio information 734to second protocol interface 710. First protocol interface 708 mayadditionally be configured to send control information 726 to mediasource device 702.

Second protocol interface 710 may be a hardware and/or softwarecomponent configured to (i) receive control information 722 from controldevice 704 and (ii) send audio information 732 to control device 704.Second protocol interface 710 may additionally be configured to (i) sendcontrol information 724 to first protocol interface 708 and (ii) receiveaudio information 734 from first protocol interface 708. Second protocolinterface 710 may additionally be configured to send and/or receivecontrol information 750 to/from second protocol interface 718.

Media renderer 712 may be a hardware and/or software componentconfigured to (i) receive audio data 738 from first protocol interface708 and (ii) render audio data 738 for playback.

Second networked device 714 may be a networked device such as any of avoice enabled device (VED), networked microphone device (NMD), audioplayback device (APD), video playback device (VPD), or any othernetworked device comprising one or more microphones and one or morespeakers. Second networked device 714 includes a first protocolinterface 716, a second protocol interface 718, and a media renderer720. Second networked device 714 may be configured to receive audiocontent 742 from media source device. First networked device 706 mayfurther be configured to send second control information 728 to mediasource device 702. Second networked device 714 may additionally beconfigured to send and/or receive control information 750 to/from firstnetworked device 706.

First protocol interface 716 may be a hardware and/or software componentconfigured to (i) receive audio content 742 sent by media source device702, (ii) convert (e.g., decrypt, decompress, and/or decode) audiocontent 742, and/or (iii) send the converted audio content 742 to mediarenderer 720. First protocol interface 716 may additionally beconfigured to (i) receive control information 730 from second protocolinterface 718 and/or (ii) send audio information 736 to second protocolinterface 718. First protocol interface 716 may additionally beconfigured to send control information 728 to media source device 702.

Second protocol interface 718 may be a hardware and/or softwarecomponent configured to send control information 730 to first protocolinterface 716. Second protocol interface 710 may additionally beconfigured to send and/or receive control information 750 to/from secondprotocol interface 710.

Media renderer 720 may be a hardware and/or software componentconfigured to (i) receive audio 744 data from first protocol interface716 and (ii) render audio data 744 for playback.

First media playback protocol 746 may be a set or system of protocolsused by media source device 702 to stream media content to firstnetworked device 706 and second networked device 714. To discovernetworked devices available for playback, first media playback protocol746 may include a discovery stage. A control device may transmit (e.g.,broadcast, multicast, unicast) a discovery message (e.g., mDNS message)to devices on the network. First networked device 706 and secondnetworked device 714 can advertise themselves by responding to thediscovery message. Media source device 702 may determine from thediscovery response message that first networked device 706 and secondnetworked device 714 support first media playback protocol 746. Forexample, the discovery response message may contain informationidentifying or listing first media playback protocol 746 as a protocolsupported by first networked device 706.

After identifying that first networked device 706 and second networkeddevice 714 support first media playback protocol 746, media sourcedevice 702 may open a connection (e.g., via real-time streaming protocol(RTSP) setup message) with first networked device 706 and a connectionwith second networked device 714. Then, media source device 702 may sendaudio content 740 using an audio stream (e.g., real-time transportprotocol (RTP) stream) which may be a unicast stream. Audio content 740may optionally contain metadata (e.g., secondary data related to themedia content) in the same stream or different stream. First networkeddevice 706 and second networked device 714 may send media playbackcontrols (e.g., play, pause, next track, and volume adjustments) tomedia source device 702 if a user inputs the commands on first networkeddevice 706, second networked device 714, control device 704, or mediasource device 702.

Second media playback protocol 748 may be a set or system of protocolsused by control device 704 to control various features of firstnetworked device 706 and second networked device 714. Second mediaplayback protocol 748 may involve the same or similar protocolsimplemented by playback device 200, control device 300, controllerinterface 400, plurality of networked devices 500, and/or networkmicrophone device 600.

In operation, media source device 702 may stream audio content 740 tofirst networked device 706. Audio content 740 may contain metadataincluding information about audio content 740 (e.g., song title,runtime, album art, artist, radio station name, etc.) First protocolinterface 708 of first networked device 706 may receive audio content740 and its corresponding metadata from media source device 702. Firstprotocol interface 708 may then decrypt, decompress audio content 740,and/or decode into audio data 738 and send audio data 738 to mediarenderer 712 for rendering and playback. First protocol interface 708may send audio information 734 to second protocol interface 710. Audioinformation 734 may contain the metadata sent with and/or correspondingto audio content 740 to first protocol interface 708 of first networkeddevice 706. Second protocol interface 710 may send audio information 732to control device 704. Audio information 732 may contain the meta datasent with and/or corresponding to audio content 740 which may becurrently played back by first networked device 706. Control device 704may display audio information 732 on a graphical interface to identifymedia currently being played back.

Media source device 702 may additionally stream audio content 742 tonetworked device 714 in an audio stream (e.g., unicast stream, multicaststream). Audio content 742 and audio content 740 may contain the samemedia content or may be different portions of the same media content.Networked device 706 and networked device 714 may play audio content740,742 in synchrony using playback timing information included withaudio content 740, 742. For example, networked device 706 and networkeddevice 714 may be grouped for synchronous media playback. As yet anotherexample, if first networked device 706 and second networked device 714are configured to operate in a stereo pair, first networked device 706may operate as a “right” speaker and second networked device 714 mayoperate as a “left speaker.” In one example, audio content 740 mayrepresent the “right” portion of the media content and audio 742 mayrepresent the “left” portion of the media content. In another example,audio content 740 and 742 may contain the same media content. Firstnetworked device 706 may extract and playback the “right” portion ofaudio content 740 and second networked device 714 may extract andplayback the “left portion” of audio content 742.

First protocol interface 716 of second networked device 714 may thenreceive audio 742 and its corresponding metadata from media sourcedevice 702. First protocol interface 716 may then decrypt, decompress,and/or decode audio content 742 into audio data 744 and send audio data744 to media renderer 720 for rendering and playback. First protocolinterface 716 may send audio information 736 to second protocolinterface 718. Audio information 736 may contain the metadata sent withaudio content 742 to first protocol interface 716.

Second protocol interface 710, after receiving audio information 734from first protocol interface 708, may convert audio information 734 toa format compatible with second media playback protocol 748 and send theconverted audio information to control device 704 as audio information732. In some aspects, second protocol interface 710 may be compatiblewith audio information 734 without conversion, or the second protocolinterface 710 may be configured to convert audio information 734.Control device 704 receives audio information 734, which allows controldevice 704 to display to the user the media content playing on firstnetworked device 706. This is beneficial because it allows a user tostart a media stream through media source device 702 and then later viewwhat is playing via control device 704.

A user may issue a playback command via control device 704 to, forexample, pause the media content. Control device 704 may send, in aformat compatible with second media playback protocol 748, the pausecommand as part of control information 722 to second protocol interface710 of first networked device 706. Second protocol interface 710 mayreceive the pause command and convert the pause command to a formatcompatible with first media playback protocol 746. Second protocolinterface 710 may send the pause command as part of control information724 to first protocol interface 708. Second protocol interface 710 mayalso send the unconverted pause command to second protocol interface 718of second networked device 714 as part of control information 750. Afterreceiving the pause command from second protocol interface 710, secondprotocol interface 718 may convert the pause command to a formatcompatible with first media playback protocol 746. Second protocolinterface 718 may send the converted pause command to first protocolinterface 716 as a part of control information 730. For example, secondprotocol interface 710 may receive the pause command as a UPnP message,and transmit an instruction to pause playback to first protocolinterface 708, and first protocol interface 708 may transmit the pauseinstruction as a RTSP request. The RTSP request may include a sessionidentifier to identify the current playback session. The sessionidentifier may be a number or string that identifies the media streamsuch as a session universally unique identifier (UUID), client-instanceinformation, or DACP-ID.

First protocol interface 708 may receive the pause command throughcontrol information 724 from second protocol interface 710 and send thepause command to media source device 702 as part of control information726. Similarly, first protocol interface 716 may receive the pausecommand as part of control information 730 from second protocolinterface 718 and send the pause command to media source 702 as part ofcontrol information 728.

Media source device 702 may receive the pause command from firstnetworked device 706 through control information 726 and from secondnetworked device 714 through control information 728. After receivingthe pause command, media source device 702 may temporarily stop sendingaudio content 740 and audio content 742 to first networked device 706and second networked device 714, respectively.

While the systems and methods described herein are described in thecontext of two networked devices (first networked device 706 and secondnetworked device 714), the methods and interactions are equallyapplicable to media playback systems including any number of networkeddevices (e.g., only one networked device or more than two networkeddevices).

III. Example Systems and Methods

One challenge for network media systems that are compatible withmultiple media playback protocols may be an inability to effectivelydisplay and stream media to grouped networked devices configured forsynchronous playback. Networked devices may be in a group when they areconfigured to play a media stream in synchrony with one another. Onemedia playback protocol may group networked devices in a particular way(e.g., network topology) that is not compatible with another mediaplayback protocol. Thus, if a user attempts to stream media to groupednetworked devices using a device that uses a different media playbackprotocol than the one that was used to initially group the networkeddevices, the device might not display the group of networked devicesaccurately on an interface of a control device, which may result in theinability to control media playback.

To address this potential problem, in some examples, it may be desirablefor a network media system to (i) form a group including one or morenetworked devices using a particular media playback protocol, (ii)determine a group coordinator for the group using the same mediaplayback protocol, and (iii) transmit to a media source device that isnot compatible with the particular media playback protocol, a groupnetwork identity using a different media playback protocol. The networkmedia system may form the group using various aspects of the systems andmethods described in FIGS. 1-7. This may allow a user to view and streammedia to the group of networked devices even though the media sourcedevice uses a different media playback protocol than was used by thenetwork media system to group the one or more networked devices. Inoperation, the network media system may have the capability tocommunicate with the networked devices in the group via one mediaplayback protocol and communicate with the media source device viaanother media playback protocol.

For purposes of the description herein, a “network media system” may bereferred to as a “media playback system” and/or “media system.” Thesereferences are not meant to be limiting and only used for effectivenessin describing the interactions between a network media system, mediasource device, and control device.

For instance, a network media system that uses a particular mediaplayback protocol (e.g., a network topology) may group one or morenetwork devices to playback media in synchrony with one another. Thenetwork media system may group the one or more networked devices inresponse to a command from a user via (i) an interface associated withone media playback protocol (e.g., a Sonos™ controller) or (ii) manualinput on one or more of the networked devices. A user may then want tostream media content to the group of networked devices using a mediasource device that uses a different media playback protocol (e.g., aniPhone® using Airplay). Because the media source device uses a differentmedia playback protocol than the media playback protocol used to groupthe one or more networked devices, the media source device and aninterface associated with the media playback protocol of the mediasource device might not reflect the networked devices as grouped forsynchronous playback even though the networked devices are playing backmedia synchronously.

The network media system may determine a group coordinator for the groupusing the same media playback protocol used to form the groups. Thegroup coordinator may be responsible for (i) receiving the media streamfrom the media source device (ii) transmitting the media stream to theother networked devices in the network media system, (iii) receivingcommands from a control device, and/or (iv) transmitting the commands tothe other networked devices in the network media system. This may bebeneficial because the group coordinator can control the timing andsynchronization of all media streams from the media source device andexecute commands received from a control device.

The network media system, after determining a group coordinator for thegroup of networked devices, may transmit a group network identity to themedia source device using the media playback protocol compatible withthe media source device. Based on the group network identity receivedfrom from the network media system, the media source device may displaythe group network identity in a user interface associated the firstmedia playback protocol (e.g., a user interface on an iPhone® displaysthe group of networked devices). This may allow the media source deviceto accurately display the group to a user on an interface of a differentmedia playback protocol than was used to initially group the networkeddevices. In operation, the media source device may transmit (e.g.,broadcast, multicast, unicast), using the media playback protocolcompatible with the media source device, a discovery message to thenetwork media system requesting a response from available networkeddevices, and causing the grouped networked devices to respond to thediscovery message broadcast over the network with the group networkidentity. Responding to the discovery message broadcast with the groupnetwork identity may create a new record within the media playbackprotocol compatible with the media source device, allowing the mediasource device to select the group of networked devices when streamingmedia content. In one example, a new mDNS record for the group name maybe added, and the new mDNS record may be included in an mDNS discoveryresponse message.

For example, in media playback system 700 in FIG. 7, first networkeddevice 706 and second networked device 714 may be grouped by mediaplayback system 700 according to second media playback protocol 748.Media playback system 700 may determine first networked device 706 isthe group coordinator of the group including first networked device 706and second networked device 714 based on second media playback protocol748. Media playback system 700 may transmit a group network identity tomedia source device 702 using first media playback protocol 746.

In some examples, the network media system transmitting a group networkidentity includes causing one or more networked devices in the group totransmit the group network identity to the media source device. Thegroup network identity may include a network device identity of one ofthe networked devices and a number one less than a number of networkeddevices within the group. For instance, the network media system maycontain three networked devices: a first networked device with a networkdevice identity of “Kitchen,” a second networked device with a networkdevice identity of “Living Room,” and a third networked device with anetwork device identity of “Bathroom.” The three networked devices maybe grouped for synchronous playback, and the network media system maycause the first networked device to transmit the group network identityof “Kitchen+2” to the media source device, which may account for thefirst networked device's network device identity and the number of othernetworked devices in the group. In operation, the first networked devicemay transmit the group network identity to the media source byresponding with the group network identity to the discovery messagetransmitted over the network. The network device identity may be thename of a network device, zone, or group of network devices which isdisplayed on an interface for playback selection. In some aspects, agroup identifier in the second media playback protocol may be mapped tothe group network identity and included in the discovery responsemessage. The mapping between the group identifier in the second mediaplayback protocol may be stored in state information of the networkmedia system.

In some examples, network media system transmitting the group networkidentity includes causing each networked device to transmit itscorresponding network device identity to the media source device. Insome circumstances, the corresponding network identities may include anindication that the networked device is in a group. This may bebeneficial because it may allow the user to view all networked devicesthat are included in the group with an indication that the networkeddevices are in a particular group. The group indication may include agroup marker such as “(G)” or other group indication icon next to thenetworked device's network device identity, or may include all networkeddevices in the group.

For example, the network media system may contain three networkeddevices: a first networked device with a network device identity of“Kitchen,” a second networked device with a network device identity of“Living Room,” and a third networked device with a network deviceidentity of “Bathroom.” The network media system may cause each of thefirst networked device, second networked device, and third networkeddevice to transmit (e.g., respond to the discovery message broadcast)their respective network identities to the media source device with anindication that the networked device is in a group. Accordingly, thefirst networked device may transmit “Kitchen (G)” or “Kitchen (groupedwith Living Room and Bathroom)” to the media source device. Inoperation, a user may select any of the networked devices with the groupindication to stream media to the whole group using the first mediaplayback protocol.

In some examples, the network media system transmitting a group networkidentity includes causing one or more networked devices in the group totransmit the group network identity to the media source device. Thegroup network identity may include a network device identity of thenetworked device transmitting the group network identity and a networkdevice identity of the networked devices not transmitting the groupnetwork identity. The networked device transmitting the group networkidentity may also transmit its network device identity along with thegroup network identity. For instance, the network media system maycontain three networked devices: a first networked device with a networkdevice identity of “Kitchen,” a second networked device with a networkdevice identity of “Living Room,” and a third networked device with anetwork device identity of “Bathroom.” The network media system maycause the first networked device to transmit (e.g., respond to thediscovery message broadcast) the group network identity of“Kitchen+Living Room+Bathroom” to the media source device. The firstnetworked device may also transmit its network device identity of“Kitchen.” This may be beneficial because it allows a user to viewand/or select just the networked device (e.g., Kitchen) or all thenetworked devices are grouped with the first networked device (e.g.,Kitchen+Living Room+Bathroom).

In some examples, at least one of the networked devices in the networkmedia system may determine which networked device should transmit thegroup network identity to the media source device. The networked devicesmay determine which networked device should transmit the group networkidentity by comparing the networked devices' network device identity.The networked devices comparing the networked devices' networkidentities may include identifying which networked device's networkdevice identity has a lower number or smaller string than othernetworked devices in the group.

For example, in FIG. 7, first networked device 706 may have a firstnetwork device identity of “0103” and second networked device 714 mayhave a second network device identity of “0921.” In this example, thefirst network device identity of “0103” is lower than the second networkdevice identity of “0921.” Since the first network device identity islower than the second network device identity, the first networkeddevice may determine it should transmit the group network identity tothe media source device. This determination may be made prior to and/orin response to receiving the discovery message from the media sourcedevice.

In some examples, a control device determines which networked device inthe group transmits the group network identity to the media sourcedevice. The control device may be a network device that is part of thenetwork media system that transmits control commands or instructions tothe networked devices using a different media playback protocol than themedia source device. The control device may be configured the same as,and operate in the substantially the same way as, control device 704 inFIG. 7. The control device may determine which networked device in thegroup transmits the group network identity to the media source devicewhen the group is formed and/or modified (e.g., adding or removingnetworked devices to the group).

For example, in FIG. 7, a user may issue a group command via controldevice 704 to group first networked device 706 and second networkeddevice 714. Based on receiving the group command, control device 704 may(i) determine that first networked device 706 should transmit the groupnetwork identity, and (ii) transmit the group command to first networkeddevice 706 as part of control information 722. Control information 722may include instructions for first networked device 706 to transmit thegroup network identity to media source device 702. First networkeddevice 706 may (i) receive the group command via second protocolinterface 710, (ii) update a group state variable in media playbacksystem 700 reflecting first networked device 706 is in a group, and/or(iii) transmit the group command to second networked device 714 as partof control information 750. Second networked device 714 may, via secondprotocol interface 718, (i) receive the group command with controlinformation 750, and (ii) update a group state variable in mediaplayback system 700 reflecting second networked device 714 is in agroup.

In some examples, the group coordinator of the network media systemdetermines which networked device in the group transmits the groupnetwork identity to the media source device. This may be beneficialbecause having one networked device (e.g., the group coordinator) in thegroup responsible for determining the networked device to transmit thegroup network identity may result in a more efficient and stream-linedprocess of transmitting the group network identity to the media sourcedevice.

For example, the network media system may contain three networkeddevices: a first networked device with a network device identity of“Kitchen,” a second networked device with a network device identity of“Living Room,” and a third networked device with a network deviceidentity of “Bathroom.” The network media system may determine the firstnetworked device is the group coordinator of the group including thethree networked devices. The first networked device may determine whichof the networked devices in the group will transmit the group networkidentity.

In some examples, the network media system determining the groupcoordinator may include determining which networked devices are enabledto receive the media stream from the media source device, and then basedon determining that one of the networked devices is enabled to receivethe media stream, determining that that networked device is the groupcoordinator. For instance, a network media system may have a firstnetworked device and a second networked device configured in a group toreceive and stream media from a media source device. The group may beconfigured using a first media playback protocol and the media sourcedevice may be configured to stream media according to a second mediaplayback protocol. The network media system may (i) determine that thefirst networked device is enabled to receive a media stream from themedia source device using the second media playback protocol, (ii)determining that the second networked device is not enabled to receive amedia stream from the media source device using the second mediaplayback protocol, and (iii) based on determining that the firstnetworked device is enabled to receive a media stream from the mediasource device using the second media playback protocol, determining thatthe first networked device is the group coordinator.

For example, in FIG. 7, a user may issue a command to stream media frommedia source device 702 in an interface using first media playbackprotocol 746. Media playback system 700 may determine first networkeddevice is enabled to receive audio content 740 via first protocolinterface 708, and second networked device 714 is not enabled to receiveaudio content 742 via first protocol interface 716. In some aspects,second networked device 714 might not be configured to have firstprotocol interface 716. Based on this determination, media playbacksystem 700 may determine that the first networked device 706 is thegroup coordinator.

In some examples, the network media system determining the groupcoordinator may include (i) receiving, via one of the networked devicesin the group from the media source device, a command to begin mediaplayback on the networked device, and (ii) in response to receiving thecommand to begin media playback on that networked device, determiningthat networked device is the group coordinator. This allows the networkmedia system to determine the group coordinator dynamically, in responseto a user's command to begin media playback on a particular networkeddevice.

For example, the network media system may contain three networkeddevices: a first networked device with a network device identity of“Kitchen,” a second networked device with a network device identity of“Living Room,” and a third networked device with a network deviceidentity of “Bathroom.” A user may issue a command to begin mediaplayback on the first networked device. The network media system maydetermine, based on the user's selection of the first networked device,that the first networked device is the group coordinator.

In some examples, after determining a networked device is the groupcoordinator based on receiving a command from the media source device tobegin media playback on that networked device, the network media systemmay additionally (i) receive, via the group coordinator and from themedia device, a media stream, and (ii) transmit, via the groupcoordinator to other members of the group, the media stream forplayback. This may be beneficial because the group coordinator cancontrol the synchronization of the media playback when it receives themedia stream and transmit the media stream to the other networkeddevices in the group.

In some circumstances, a user may desire to stream media content, viamedia source device using an interface of a first media playbackprotocol, to a group of networked devices that was formed using a secondmedia playback protocol. However, the media source device might not beable to stream to the group because it is not compatible with the secondmedia playback protocol used to group the networked devices. To overcomethis potential problem, the second media playback protocol correspondingto the control device may have settings to enable media streaming from amedia source device using the first media playback protocol. Forinstance, the settings may include an option to “include grouped zones”that, when enabled, allows the media source device to stream mediacontent to groups formed using the second media playback protocol. Insome aspects, tf a user enabled the “include grouped zones” playbacksetting on the control device, the media source device may stream mediacontent to a particular networked device, and the particular networkeddevice may transmit the media stream to other networked devices in thegroup using the second media playback protocol.

In some examples, once a user enables the “include grouped zones”functionality described above, a first networked device in the networkmedia system may receive, from a media source device, a media streamusing a first media playback protocol, where the media source device andthe first networked device are configured to use a first media playbackprotocol and a second media playback protocol, and where the first mediaplayback protocol and the second media playback protocol areincompatible, and where the first media playback protocol includes thefirst media playback protocol. The first network device may alsoreceive, from a second networked device, an indication to join a groupwith the first networked device using the second media playbackprotocol. The first network device may also form a group comprising thefirst networked device and the second networked device using the firstmedia playback protocol.

For example, in FIG. 7, a user may enable an “include grouped zones”setting on control device 704 in an interface according to second mediaplayback protocol 748. Control device 704 may transmit an indicationthat the “include grouped zones” setting is enabled to first networkeddevice 706 via control information 722. First networked device 706 mayforward the indication to second networked device 714 via controlinformation 750. First networked device 706 may also transmit theindication to media source device 702 via first protocol interface 708.Media source device 702 may begin streaming audio content 740 to firstnetworked device 706 via first protocol interface 708. A user may thenissue a command to second networked device 714 to join a group withfirst networked device 706. In response to the command, first networkeddevice 706 may form a group with second networked device 714 inaccordance with second media playback protocol 748.

In some examples, once a user enables the “include grouped zones”functionality, each networked device's group state variables in thenetwork topology corresponding to the second media playback protocol maybe included in their respective network identities transmitted to themedia source device using the first media playback protocol. Forinstance, if a user enables the “include grouped zones” setting and agroup is formed in the second media playback protocol including a firstnetworked device and a second networked device, the first and secondnetworked devices may transmit (e.g., respond to the discovery messagebroadcast) their group state variables device (e.g., Kitchen ‘groupedwith Living Room’), indicating to the media source device the group towhich the networked device belongs and may transmit their individualnetwork device identities in addition to their group state variables. Ifthe “include grouped zones” functionality is not enabled, the first andsecond networked devices may transmit their individual network deviceidentities and might not transmit group state information to the mediasource device.

In some examples, the indication to join a group may be a message fromthe second networked device to join the group with the first networkeddevice. The message may be sent from the second networked device tomedia source device in response to a user's command to join the group inan interface of the second media playback protocol. The message may be afirst media playback protocol request that media source device send, tothe second networked device, the same audio content received by thefirst networked device for synchronous playback with media sourcedevice. The message may include a session identifier of the playbacksession of the first networked device and/or a network device identityof the second networked device.

In some examples, the indication to join the group may include a commandfrom a local interface of the second networked device to join the groupwith the first networked device. The local interface of the secondnetworked device may include hardware components configured tofacilitate grouping with other networked devices. For instance, thesecond networked device may have a button that when pressed and held bya user, joins the last group formed on the network. In operation, when auser presses and holds the button (e.g., issues a command to join thelast group formed), the second networked device may send an indicationto the first networked device to join the group.

In some examples, the first networked device may (i) determine that thesecond networked device is enabled to receive the media stream from themedia source device using the first media playback protocol, and (ii) inresponse to determining that the second networked device is enabled toreceive the media stream from the media source device using the firstmedia playback protocol, transmit, to the media source device, a commandto transmit the media stream to the second networked device. This may bebeneficial in situations where the first networked device has limitedresources to receive and transmit a media stream to other networkeddevices in the group. This allows the first networked device to issue acommand to the media source device, informing the media source devicethat the second networked device is compatible with the first mediaplayback protocol, and instructing the media source device to streammedia content directly to the second networked device.

For example, in FIG. 7, first networked device 706 may determine thatsecond networked device 714 is enabled to receive audio content 742 frommedia source device 702. First networked device 706 may determine thatsecond networked device 714 is enabled to receive audio content 742 bydetermining second networked device 714 has first protocol interface716. In response to determining second networked device 714 is enabledto receive audio content 742 from media source device 702, firstnetworked device 714 may transmit, via first protocol interface 708, acommand to media source device 702 to begin streaming audio content 742to second networked device 714.

In some situations, after forming a group, it may be desirable to removeone or more networked devices from the group. In some examples, thefirst networked device may (i) receive a command to remove the firstnetworked device from the group, and (ii) in response to receiving thecommand, sending, to the media source device, a command to disconnectfrom the media source device. The first networked device may, inresponse to receiving the command, stop playback of the media stream.This may be beneficial because ungrouping networked devices in the firstmedia playback protocol may be different than ungrouping networkeddevices in the second media playback protocol. For instance, ungroupingnetworked devices in the first media playback protocol may involvesending a “disconnect” message to a media source device, whileungrouping networked devices in a second media playback protocol mayinvolve changing group state variables and/or updating a networktopology to reflect that the networked device leaving the group is nolonger in the group.

For example, in FIG. 7, a user may issue a command via control device704 to ungroup first networked device 706 from the group. Control device704 may send the ungroup command with control information 722 to secondprotocol interface 710 of first networked device 706. Second protocolinterface 710 may convert the ungroup command to be compatible withfirst media playback protocol 746 and send the converted ungroup commandto first protocol interface 708 as part of control information 724. Theconverted ungroup command may be a disconnect command in first mediaplayback protocol 746. First networked device 706, via first protocolinterface 708, may (i) send the disconnect command to media sourcedevice 702 as part of control information 726, and (ii) stop sendingaudio data 738 to media renderer 712, stopping playback of the mediacontent. First networked device 706 may stop sending audio data 738 tomedia renderer 712 prior to receiving back the disconnect command frommedia source device 702 and/or prior to the media source device 702ceasing transmission of audio content 740.

a. Example Methods

Method 800 in FIG. 8 and method 900 in FIG. 9 shows an example of amethod that can be implemented within an operating environment includingor involving, for example, the media playback system 100 of FIG. 1, oneor more playback devices 200 of FIG. 2, one or more control devices 300of FIG. 3, the user interface of FIG. 4, the configuration shown in FIG.5, the NMD shown in FIG. 6, and/or the media playback system 700 in FIG.7.

Method 800 may include one or more operations, functions, or actions asillustrated by one or more of blocks 802, 804, and 806. Method 900 mayinclude one or more operations, functions, or actions as illustrated byone or more of blocks 902, 904, and 906. Although the blocks areillustrated in sequential order, these blocks may also be performed inparallel, and/or in a different order than those described herein. Also,the various blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon the desired implementation.

In addition, for method 800, method 900, and other processes and methodsdisclosed herein, the flowchart shows functionality and operation of onepossible implementation of some examples. In this regard, each block mayrepresent a module, a segment, or a portion of program code, whichincludes one or more instructions executable by one or more processorsfor implementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive. Thecomputer readable medium may include non-transitory computer readablemedium, for example, such as tangible, non-transitory computer-readablemedia that stores data for short periods of time like register memory,processor cache and Random Access Memory (RAM). The computer readablemedium may also include non-transitory media, such as secondary orpersistent long term storage, like read only memory (ROM), optical ormagnetic disks, compact-disc read only memory (CD-ROM), for example. Thecomputer readable media may also be any other volatile or non-volatilestorage systems. The computer readable medium may be considered acomputer readable storage medium, for example, or a tangible storagedevice. In addition, for the method 800, method 900, and other processesand methods disclosed herein, each block in FIG. 8 and FIG. 9 mayrepresent circuitry that is wired to perform the specific logicalfunctions in the process.

Method 800 begins at block 802, which includes a network media system(such as a computing device configured to control the network mediasystem), forming a group including a first networked device and a secondnetworked device using a first media playback protocol. The networkmedia system may include the first networked device and the secondnetworked device.

Next, method 800 advances to block 804, which includes, determining agroup coordinator for the group using the first media playback protocol.

Next, method 800 advances to block 806, which includes, transmitting, toa media source device, a group network identity using a second mediaplayback protocol. The media source device and one of the firstnetworked device and the second networked device are configured to usethe first media playback protocol and the second media playbackprotocol. The first media playback protocol and the second mediaplayback protocol are incompatible.

In some examples, transmitting the group network identity may include(i) transmitting, using the second media playback protocol, a discoverymessage to the first networked device and the second networked device,and (ii) causing one of the first networked device and the secondnetworked device to respond to the discovery message with the groupnetwork identity.

In some examples, transmitting the group network identity may includecausing one of the first networked device and the second networkeddevice to transmit the group network identity to the media sourcedevice. The group network identity may include (i) a network deviceidentity of one of the first networked device and the second networkeddevice, and (ii) a number one less than a number of networked deviceswithin the group.

In some examples, transmitting the group network identity may include(i) causing the first networked device to transmit a first networkdevice identity to the media source device, and (ii) causing the secondnetworked device to transmit a second network device identity to themedia source device. In these examples, the first network deviceidentity and the second network device identity include an indicationthat the first networked device and second networked device are in thegroup.

In some examples, transmitting the group network identity may includecausing one of the first networked device and the second networkeddevice to transmit the group network identity. The group networkidentity may include (i) a first network device identity of one of thefirst networked device and the second networked device, and (ii) asecond network device identity of the other one of the first networkeddevice and second networked device. In some examples, the groupcoordinator determines that the first networked device is to transmitthe group network identity. In other examples, at least one the firstnetworked device and the second networked device determines that thefirst networked device is to transmit the group network identity bycomparing the first network device identity and the second networkdevice identity. In further examples, a control device determines thatthe first networked device is to transmit the group network identity,wherein the network media system further includes the control device. Insome examples, the control device comprises the media source device.

In some examples, determining the group coordinator for the groupincludes (i) receiving, via the first networked device from the mediasource device, a command to begin media playback on the first networkeddevice, and (ii) in response to receiving the command to begin mediaplayback on the first networked device, determining that the firstnetworked device is the group coordinator.

In some examples, determining the group coordinator for the groupincludes (i) determining that the first networked device is enabled toreceive a media stream from the media source device using the secondmedia playback protocol, (ii) determining that the second networkeddevice is not enabled to receive a media stream from the media sourcedevice using the second media playback protocol, and (iii) based ondetermining that the first networked device is enabled to receive amedia stream from the media source device using the second mediaplayback protocol, determining that the first networked device is thegroup coordinator.

Some examples further include (i) receiving, from the media sourcedevice, a command to begin playing a media stream on the first networkeddevice, (ii) in response to receiving the command to begin mediaplayback on the first networked device, determining that the firstnetworked device is the group coordinator, (iii) receiving, via thefirst networked device from the media source device, a media steam, and(iv) based on determining that the first networked device is the groupcoordinator, transmitting, via the first networked device to the secondnetworked device, the media stream for playback.

Method 900 begins at block 902, which includes a first networked device(or alternatively a computing device configured to control the firstnetworked device) receiving, from a media source device, a media streamusing a first media playback protocol. The media source device and thefirst networked device are configured to use a first media playbackprotocol and a second media playback protocol. The first media playbackprotocol and the second media playback protocol are incompatible. Thefirst media playback protocol comprises the first media playbackprotocol.

Next, method 900 advances to block 904, which receiving, from a secondnetworked device, an indication to join a group with the first networkeddevice using the second media playback protocol.

Next, method 900 advances to block 906, which includes forming a groupcomprising the first networked device and the second networked deviceusing the first media playback protocol.

In some examples, the indication to join the group comprises a messagefrom the second networked device to join the group with the firstnetworked device. In some examples, the indication to join the groupcomprises a command from a local interface of the second networkeddevice to join the group with the first networked device.

Some examples further include (i) determining that the second networkeddevice is enabled to receive the media stream from the media sourcedevice using the first media playback protocol, and (ii) in response todetermining that the second networked device is enabled to receive themedia stream from the media source device using the first media playbackprotocol, transmitting, to the media source device, a command totransmit the media stream to the second networked device.

Some examples further include (i) determining that the second networkeddevice is not configured to receive the media stream from the mediasource device using the first media playback protocol, and (ii) inresponse to determining that the second networked device is notconfigured to receive the media stream from the media source deviceusing the first media playback protocol, transmitting, to the secondnetworked device, the media stream.

Some examples further include (i) receiving a command to remove thefirst networked device from the group, and (ii) in response to receivingthe command, sending, to the media source device, a command todisconnect from the media source device. These alternative examples mayfurther include in response to receiving the command, stopping playbackof the media stream.

IV. Conclusion

The description above discloses, among other things, various examplesystems, methods, apparatus, and articles of manufacture including,among other components, firmware and/or software executed on hardware.It is understood that such examples are merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of the firmware, hardware, and/or software aspects or componentscan be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, the examples provided are not the onlyway(s) to implement such systems, methods, apparatus, and/or articles ofmanufacture.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of aninvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible,non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on,storing the software and/or firmware.

What is claimed is:
 1. A first playback device comprising: at least oneprocessor; non-transitory computer-readable medium; and programinstructions stored on the non-transitory computer-readable medium thatare executable by the at least one processor such that the playbackdevice is configured to: while the first playback device is a member ofa synchronous media playback group with a second playback device using afirst media playback protocol, and after a particular playback settingis enabled using the first media playback protocol, receive, using asecond media playback protocol from a media source device, a first mediastream comprising audio data for playback, wherein the first mediaplayback protocol and the second media playback protocol areincompatible; determine that the particular playback setting is enabledand that the synchronous media playback group comprises the firstplayback device and the second playback device; and after determiningthat the particular playback setting is enabled and that the synchronousmedia playback group comprises the first playback device and the secondplayback device, (i) generate a second media stream based on thereceived first media stream, wherein the second media stream comprisesinformation for synchronous playback with the first playback device, and(ii) transmit, to the second playback device, the second media streamusing the second media playback protocol.
 2. The first playback deviceof claim 1, wherein the first playback device is configured to use boththe first media playback protocol and the second media playbackprotocol, and wherein the second playback device is configured to usethe first media playback protocol and not the second media playbackprotocol.
 3. The first playback device of claim 1, further comprisingprogram instructions stored on the non-transitory computer-readablemedium that are executable by the at least one processor such that thefirst playback device is configured to: receive, using the first mediaplayback protocol, a command to enable the particular playback setting;and after receiving the command to enable the particular playbacksetting, configure the first playback device to transmit a media streamreceived via the second media playback protocol using the first mediaplayback protocol.
 4. The first playback device of claim 3, wherein theprogram instructions that are executable by the at least one processorsuch that the first playback device is configured to receive, using thefirst media playback protocol, the command to enable the particularplayback setting comprise program instructions that are executable bythe at least one processor such that the first playback device isconfigured to: receive, from the media source device using the firstmedia playback protocol, the command to enable the particular playbacksetting.
 5. The first playback device of claim 3, wherein the programinstructions that are executable by the at least one processor such thatthe first playback device is configured to receive, using the firstmedia playback protocol, the command to enable the particular playbacksetting comprise program instructions that are executable by the atleast one processor such that the first playback device is configuredto: receive, from a third playback device using the first media playbackprotocol, the command to enable the particular playback setting, whereinthe third playback device is separate from the media source device, thefirst playback device, and the second playback device.
 6. The firstplayback device of claim 1, further comprising program instructionsstored on the non-transitory computer-readable medium that areexecutable by the at least one processor such that the first playbackdevice is configured to: transmit, to the media source device using thesecond media playback protocol, a group network identity identifying thefirst playback device and the second playback device.
 7. The firstplayback device of claim 1, further comprising program instructionsstored on the non-transitory computer-readable medium that areexecutable by the at least one processor such that the first playbackdevice is configured to: receive, using the first media playbackprotocol, a command to form the synchronous media playback group withthe second playback device; and form, using the first media playbackprotocol, the synchronous media playback group comprising the firstplayback device and the second playback device.
 8. The first playbackdevice of claim 7, wherein the program instructions that are executableby the at least one processor such that the first playback device isconfigured to receive, using the first media playback protocol, thecommand to form the synchronous media playback group with the secondplayback device comprise program instructions that are executable by theat least one processor such that the first playback device is configuredto: receive, from the media source device using the first media playbackprotocol, the command to form the synchronous media playback group withthe second playback device.
 9. A non-transitory computer-readablemedium, wherein the non-transitory computer-readable medium isprovisioned with program instructions that, when executed by at leastone processor, cause a first playback device to: while the firstplayback device is a member of a synchronous media playback group with asecond playback device using a first media playback protocol, and aftera particular playback setting is enabled using the first media playbackprotocol, receive, using a second media playback protocol from a mediasource device, a first media stream comprising audio data for playback,wherein the first media playback protocol and the second media playbackprotocol are incompatible; determine that the particular playbacksetting is enabled and that the synchronous media playback groupcomprises the first playback device and the second playback device; andafter determining that the particular playback setting is enabled andthat the synchronous media playback group comprises the first playbackdevice and the second playback device, (i) generate a second mediastream based on the received first media stream, wherein the secondmedia stream comprises information for synchronous playback with thefirst playback device, and (ii) transmit, to the second playback device,the second media stream using the second media playback protocol. 10.The non-transitory computer-readable medium of claim 9, wherein thefirst playback device is configured to use both the first media playbackprotocol and the second media playback protocol, and wherein the secondplayback device is configured to use the first media playback protocoland not the second media playback protocol.
 11. The non-transitorycomputer-readable medium of claim 9, wherein the non-transitorycomputer-readable medium is also provisioned with program instructionsthat, when executed by at least one processor, cause the first playbackdevice to: receive, using the first media playback protocol, a commandto enable the particular playback setting; and after receiving thecommand to enable the particular playback setting, configure the firstplayback device to transmit a media stream received via the second mediaplayback protocol using the first media playback protocol.
 12. Thenon-transitory computer-readable medium of claim 11, wherein the programinstructions that, when executed by at least one processor, cause thefirst playback device to receive, using the first media playbackprotocol, the command to enable the particular playback setting compriseprogram instructions that, when executed by at least one processor,cause the first playback device to: receive, from the media sourcedevice using the first media playback protocol, the command to enablethe particular playback setting.
 13. The non-transitorycomputer-readable medium of claim 9, wherein the non-transitorycomputer-readable medium is also provisioned with program instructionsthat, when executed by at least one processor, cause the first playbackdevice to: transmit, to the media source device using the second mediaplayback protocol, a group network identity identifying the firstplayback device and the second playback device.
 14. The non-transitorycomputer-readable medium of claim 9, wherein the non-transitorycomputer-readable medium is also provisioned with program instructionsthat, when executed by at least one processor, cause the first playbackdevice to: receive, using the first media playback protocol, a commandto form the synchronous media playback group with the second playbackdevice; and form, using the first media playback protocol, thesynchronous media playback group comprising the first playback deviceand the second playback device.
 15. The non-transitory computer-readablemedium of claim 14, wherein the program instructions that, when executedby at least one processor, cause the first playback device to receive,using the first media playback protocol, the command to form thesynchronous media playback group with the second playback devicecomprise program instructions that, when executed by at least oneprocessor, cause the first playback device to: receive, from the mediasource device using the first media playback protocol, the command toform the synchronous media playback group with the second playbackdevice.
 16. A method carried out by a first playback device, the methodcomprising: while the first playback device is a member of a synchronousmedia playback group with a second playback device using a first mediaplayback protocol, and after a particular playback setting is enabledusing the first media playback protocol, receiving, using a second mediaplayback protocol from a media source device, a first media streamcomprising audio data for playback, wherein the first media playbackprotocol and the second media playback protocol are incompatible;determining that the particular playback setting is enabled and that thesynchronous media playback group comprises the first playback device andthe second playback device; and after determining that the particularplayback setting is enabled and that the synchronous media playbackgroup comprises the first playback device and the second playbackdevice, (i) generating a second media stream based on the received firstmedia stream, wherein the second media stream comprises information forsynchronous playback with the first playback device, and (ii)transmitting, to the second playback device, the second media streamusing the second media playback protocol.
 17. The method of claim 16,wherein the first playback device is configured to use both the firstmedia playback protocol and the second media playback protocol, andwherein the second playback device is configured to use the first mediaplayback protocol and not the second media playback protocol.
 18. Themethod of claim 16, further comprising: receiving, using the first mediaplayback protocol, a command to enable the particular playback setting;and after receiving the command to enable the particular playbacksetting, configuring the first playback device to transmit a mediastream received via the second media playback protocol using the firstmedia playback protocol.
 19. The method of claim 18, wherein receiving,using the first media playback protocol, the command to enable theparticular playback setting comprises: receiving, from the media sourcedevice using the first media playback protocol, the command to enablethe particular playback setting.
 20. The method of claim 15, furthercomprising: receiving, using the first media playback protocol, acommand to form the synchronous media playback group with the secondplayback device; and forming, using the first media playback protocol,the synchronous media playback group comprising the first playbackdevice and the second playback device.